Aligning parameter data with audio recordings

ABSTRACT

Various techniques relate to aligning parameters and audio recordings obtained at a rescue scene. An example method includes receiving, from a first device, a first file including first measurements of a first parameter at first discrete times in a time interval. The first file further indicates a marker output by the first device during the time interval. The method also includes receiving, from a second device, a second file comprising second measurements of a second parameter at second discrete times in the time interval. The method includes detecting the marker output by the first device in the second measurements of the second parameter and based on detecting the signal output by the first device in the second measurements, generating aligned data by time-aligning the first measurements of the first parameter and the second measurements of the second parameter. The method further includes outputting the aligned data.

CROSS-REFERENCE TO RELATED APPLICATION

This application claims the benefit of U.S. Provisional Application No.63/222,937, which was filed on Jul. 16, 2021 and is incorporated byreference herein in its entirety.

BACKGROUND

Many emergency service providers use recorders to document emergencyscenes. For example, an emergency medical service (EMS) respondercarries and activates an independent audio recorder when they respond toan emergency event. The obtained audio recording can be used forpost-event review and documentation. However, in some cases, it isdifficult to identify the time interval documented in the audiorecording. With organizations that have multiple responders and multiplerecordings, it can be difficult to identify which audio recordingscorrespond to which emergency events.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 illustrates an example environment for synchronizing differenttypes of captured data.

FIG. 2 illustrates an example of a parameter file described withreference to FIG. 1 .

FIG. 3 illustrates an example of a recording file described withreference to FIG. 1 .

FIG. 4 illustrates an example of aligned data described with referenceto FIG. 1 .

FIG. 5 illustrates an example of a report described with reference toFIG. 1 .

FIG. 6 illustrates an example rescue scene associated with an alternatetechnique for aligning a recording file and a parameter file obtained bythe medical device.

FIG. 7 illustrates an example process for aligning parameter data and anaudio recording.

FIG. 8 illustrates an example of an external defibrillator configured toperform various functions described herein.

DETAILED DESCRIPTION

FIG. 1 illustrates an example environment 100 for synchronizingdifferent types of captured data. As shown, the environment 100 includesa rescue scene 102 in which a rescuer 104 is treating a patient 106. Therescue scene 102, in some implementations, is a geographic area, volume,or other physical environment. In some examples, the rescue scene 102 isoutside of a formal, clinical environment (e.g., a hospital). Forexample, the rescue scene 102 is outdoors, in a school, in an airport,or some other non-clinical building. The rescuer 104 is an individualcaring for the patient 106. Examples of the rescuer 104 include abystander, an emergency medical service provider or another type of careprovider, such as a nurse, physician, or physician's assistant. Thepatient 106 is an individual being cared for by the rescuer 104. Invarious implementations, the patient 106 is experiencing acute distressand/or a medical emergency. In some examples, the patient 106 isexperiencing cardiac arrest.

The rescuer 104 uses a medical device 108 to diagnose the patient 106,treat the patient 106, or both. In some examples, the medical device 108is a defibrillator, such as a monitor-defibrillator or an automatedexternal defibrillator (AED). In some cases, the medical device 108 isan ultrasound device configured to generate an ultrasound image of thepatient 106 and/or to detect a blood pressure of the patient 106. Insome examples, the medical device 108 is a ventilation device configuredto provide assisted ventilation to the patient 106. The medical device108, in various implementations, includes one or more sensors configuredto detect a physiological parameter of the patient 106. As used herein,the term “physiological parameter,” and its equivalents, may refer to avital sign or other metric indicative of a condition of an individual.For instance, the medical device 108 includes a detection circuitelectrically coupled to electrodes that are disposed on the chest of thepatient 106, wherein the detection circuit is configured to detect atransthoracic impedance of the patient 106, an electrocardiogram (ECG)of the patient 106, or a combination thereof. Other examples ofphysiological parameters include an oxygenation of the patient's 106blood (e.g., a peripheral (SpO₂) and/or regional oxygenation level), anamount of carbon dioxide in the patient's 106 breath (e.g., a capnographand/or end tidal CO₂ (EtCO₂)), a heart rate of the patient 106, a bloodpressure of the patient 106, a carboxyhemoglobin level of the patient's106 blood, a temperature of the patient 106, a respiration rate of thepatient 106, and a pulse rate of the patient 106.

In some examples, the medical device 108 includes one or more therapycircuits, one or more mechanical devices, or any combination thereof,which are configured to administer a therapy to the patient 106. Forexample, the medical device 108 can include a discharge circuit thatoutputs an electrical signal to electrodes disposed on the chest of thepatient 106. In some cases, the electrical signal is in the form of adefibrillation shock, a pacing signal, or a synchronized cardioversionsignal.

The medical device 108 further includes a speaker 110 configured tooutput an audible marker 112 into the rescue scene 102. The audiblemarker 112 is a sound output by the speaker 110 of the medical device108. Examples of the audible marker 112 include a start-up sound of themedical device 108 (e.g., a sound that the medical device 108 outputswhen the medical device 108 powers up), a shut-down sound of the medicaldevice 108 (e.g., a sound that the medical device 108 outputs when themedical device 108 turns off), an audible prompt output by the medicaldevice 108 (e.g., an instruction output by the medical device 108 to therescuer 104 related to care of the patient 106), an alarm output by themedical device 108, or any other type of sound output by the medicaldevice 108. In some implementations, the medical device 108 outputs theaudible marker 112 multiple times (e.g., periodically), to allow formultiple opportunities for synchronization during the rescue event. Theaudible marker 112 is a predetermined sound, in some cases. As usedherein, the term “audible prompt,” and its equivalents, may refer to asound that instructs a user to perform an action in furtherance oftreating a patient. For example, the medical device 108 outputs anaudible prompt instructing the rescuer 104 to check a placement ofelectrodes on the chest of the patient 106, to remove hands from thepatient 106 before a defibrillation shock is administered to the patient106 by the medical device 108, or to administer the defibrillation shockto the patient 106. As used herein, the term “alarm,” and itsequivalents, may refer to a condition of a device or patient that hascrossed at least one predetermined threshold. For example, the medicaldevice 108 may output an audible alarm if the heart rate of the patient106 is above a first threshold or below a second threshold. Although notspecifically illustrated in FIG. 1 , in some cases, the audible marker112 is another type of sound output by the medical device 108, such as asound of an electrical shock output by the medical device 108 fordefibrillating the patient 106. According to some implementations, thespectral content of the audible marker 112 is configured to bediscernible in noisy environments (e.g., environments with greater thana threshold noise level). For instance, the audible marker 112 includesmultiple harmonics of a base audio signal, such that even if the baseaudio signal is masked by ambient sound in the rescue scene 102, theharmonics are unlikely to also be masked by the ambient sound. Examplesof such spectral content is described in U.S. Pub. No. 2020/0009495,which is incorporated by reference herein in its entirety. In somecases, the audible marker 112 is not perceptible by human hearing. Forinstance, the audible marker 112 is a sound below 20 Hz and/or above 20kHz. Accordingly, the audible marker 112 can be prevented fromdistracting the rescuer 104.

The audible marker 112 is output into the rescue scene 102 and detectedby a recorder 114. The recorder 114, for example, includes a microphoneconfigured to detect sound. In some examples, the recorder 114 is acomputing device, such as a mobile phone, wearable device, or the like.The recorder 114 is carried by, or otherwise associated with, therescuer 104 in some implementations.

The recorder 114 is separate from the medical device 108. Integrating arecorder into medical devices, such as defibrillators, is challengingand expensive. For example, such an integrated recorder generates asignificant amount of data that would take up a data processing channelof the medical device 108. Further, the medical device 108 generatesvarious sounds (e.g., the audible marker 112) that are difficult toshield from an integrated recorder. Furthermore, delicate electronics inan integrated recorder are difficult to electrically isolate fromcircuitry in medical devices, particularly medical devices configured tooutput high-energy electrical signals like defibrillation shocks. Bykeeping the recorder 114 separate from the medical device 108, themechanical and electrical design of the medical device 108 can besimplified. In some implementations, the recorder 114 refrains from, oris incapable of, directly communicating with the medical device 108.

In various implementations, the recorder 114 also detects other types ofsound in the rescue scene 102. For instance, the recorder 114 alsodetects a voice of the patient 106, the rescuer 104, or both. Therescuer 104, for example, audibly narrates the results of diagnostictests and/or treatments performed on the patient 106. That is, therescuer 104 can make voice notations that are detected by the recorder114. For instance, the rescuer 104 remarks out loud that “a sedative hasbeen administered” to the patient 106 prior to intubation. The rescuer104, in some cases, narrates observations of the patient 106 and therescue scene 102. For instance, the rescuer remarks that the patient 106is “unresponsive.” The recorder 114 also detects any sounds made by therescuer 104 that are not specifically directed to the recorder 114 ortreating the patient 102. In some examples, the recorder 114 detectsconversations, orders, or other types of voice notations between therescuer 104 and other individuals at the rescue scene 102. Varioussounds that are spoken by the patient 106, the rescuer 104, or otherindividuals are detected by the recorder 114.

The recorder 114 generates a recording file 116 based on the sound inthe rescue scene 102. As used herein, the term “file” and itsequivalents may refer to a collection of data stored in a single unit.In some cases, each file is identified by a file name. The medicaldevice 108 generates a parameter file 118 based on one or morephysiological parameters of the patient 106. In some cases, theparameter file 118 includes data indicating physiological parameter(s)of the patient 106 over time. For instance, the parameter file 118includes values of the physiological parameter(s). The parameter file118, in some cases, also indicates when the audible marker 112 wasoutput by the medical device 108. In various implementations, it isadvantageous to synchronize the recording file 116 and the parameterfile 118. For example, a voice notation by the rescuer 104 indicates asymptom of the patient 106 at a particular time. If the physiologicalparameter(s) of the patient 106 at the particular time are also known, acare provider 120 may be able to accurately diagnose a conditionexperienced by the patient 106 at the rescue scene 102.

The recorder 114 transmits the recording file 116 to a synchronizer 122.In addition, the medical device 108 transmits the parameter file 118 tothe synchronizer 122. The synchronizer includes hardware (e.g., aprocessor configured to perform operations), software (e.g.,instructions stored in memory that, when executed by a processor, causethe processor to perform operations), or both. In variousimplementations, the synchronizer 122 includes one or more computingdevice configured to execute software instructions. In some cases, therecording file 116 and/or the parameter file 118 are transmitted overone or more intermediary communication networks, such as at least onewired network (e.g., an electrical cable and/or an optical cable) and/orone or more wireless networks (e.g., a BLUETOOTH® network; a near fieldcommunication (NFC) network; a WI-FI® network; a 3^(rd) GenerationPartnership Project (3GPP) network, such as a Long Term Evolution (LTE)or New Radio (NR) radio access network (RAN); etc.).

The synchronizer 122 is configured to align the sound recorded in therecording file 116 with the parameter(s) indicated in the parameter file118. In particular, the synchronizer 122 is configured to detect theaudible marker 112 recorded in the recording file 116. Once the audiblemarker 112 is detected, the synchronizer 122 generates aligned data 124by time-aligning the parameter(s) in the parameter file 116 with therecording in the recording file 116. The aligned data 124, for example,includes at least two data channels: one channel including the soundrecorded by the recorder 114 and another channel including theparameter(s) detected by the medical device 108. In some examples, thesynchronizer 122 outputs the aligned data 124 to a playback device 126.The playback device 126, for example, is a computing device configuredto output an indication of the parameter(s) while also outputting thetime-aligned recorded sound. The indication of the parameter(s) is avideo of waveforms of the parameter(s), in some cases. For example, theplayback device 126 outputs the parameter(s) and the recorded sound to auser performing post-event review of the patient 106 at the rescue scene102.

In some implementations, the synchronizer 122 performs further analysison the aligned data 124. For example, the synchronizer 122 includes aspeech-to-text functionality that converts the recorded voice of therescuer 104 into a readable text file. In some implementations, thesynchronizer 122 recognizes audible commands issued by the rescuer 104in the rescue scene 102 using voice recognition techniques. In someimplementations, the synchronizer 122 automatically identifies asuspected condition of the patient 106 based on the recording file 116and/or the parameter file 118. The synchronizer 122 generates a report128 based on the results of the analysis. For example, the report 128includes the parameter(s) detected by the medical device 108, therecorded sound detected by the recorder 114, a text version of the voiceof the rescuer 104, commands issued by the rescuer 104, a suspectedcondition of the patient 106, or any combination thereof. In variousimplementations, the report 128 further indicates the times at whichdifferent events occurred at the rescue scene 100. For example, thereport 128 indicates when the parameter(s) were detected by the medicaldevice 108, when the rescuer 104 observed something about the patient106 (e.g., that the patient was unresponsive), when the rescuer 104administered a treatment to the patient 106 (e.g., when the patient wasadministered the sedative), or other events discernable based on therecording file 116 and/or the parameter file 118.

In various implementations, the synchronizer 122 performs speech-to-texton the recording file 116 and/or the aligned data 124. For example, thesynchronizer 122 includes, stores, or otherwise utilizes a Hidden MarkovModel (HMM), a dynamic time warping (DTVV) model, one or more neuralnetworks, or any combination thereof, to identify spoken words in therecording file 116 and/or the aligned data 124. In some cases, thesynchronizer 122 generates text data based on the words captured in therecording file 116 and/or the aligned data 124. The text data, forexample, is included or otherwise used to generate the report 128.

The synchronizer 122 outputs the report 128 to a clinical device 130,for example. In various implementations, the clinical device 130 is acomputing device configured to output at least a portion of the report128 to the care provider 120 or to another user. Accordingly, the careprovider 120 is provided additional context about the patient 106. Insome cases, the report 128 enhances the care provider's 120understanding of the condition of the patient 106 before the patient 106is transferred to the care provider 120 for additional care.

Although the foregoing description of FIG. 1 provides an example inwhich a physiological parameter of the patient 106 is aligned with anaudio recording of the rescue scene, implementations are not so limited.Similar techniques can be utilized to align other types of data. In someexamples, a system analyzes an audio recording of a crime scene toidentify the sound of a gunshot and, in response to the sound of the gunshot, to automatically notify a law enforcement agency. In someinstances, a system analyzes an audio recording of respiration sounds ofa patient being ventilated (e.g., using a bag-valve mask) and determinesa respiratory rate of the patient (e.g., even if a CO₂ sensor, which maynormally detect the respiratory rate, may not detect CO₂ from thepatient's airway).

In particular examples, an in-vehicle sensor is installed in a vehicle(e.g., a car, a plane, a bus, a train, or the like) and is configured todetect a parameter of the vehicle. For instance, the sensor detects anacceleration or speed of the vehicle. In addition, a computing device(e.g., a mobile phone) is located in the vehicle and detects audiowithin the vehicle. The vehicle experiences an event (e.g., a crash orcollision) while the in-vehicle sensor is detecting the parameter andthe computing device is detecting the audio. Using similar techniques tothose described above, the parameter detected by the in-vehicle sensorand the audio detected by the computing device is aligned for post-eventreview. In some cases, the synchronizer 122 detects the event based onthe recorded parameter and the audio recording. For instance, an abruptchange in acceleration detected by the in-vehicle sensor is indicativeof a crash, and a sound in the audio recording indicating the crash mayalso be identified using signal processing techniques. Alternatively,the in-vehicle sensor outputs a known sound that is detected in theaudio recording. The synchronizer 122 aligns the recorded parameter andthe audio recording. In some cases, the aligned parameter and audiorecording can be viewed for post-event review. For example, a user mayreview aligned data from a crash experienced by a driver to determinewhether the driver was distracted prior to the crash to indicate whetherthe driver was at fault for the crash, or may identify if other soundsindicative of other factors (e.g., a portion of the vehicle failingprior to the crash) may indicate that the driver was not at fault forthe crash. The aligned data 124 and/or report 128 reflecting therecording file 116 and parameter file 118 detected during the crash canbe transmitted to various devices for playback and/or post-event review.

Although FIG. 1 has been described with respect to a single parameterfile and a single recording file, implementations are not so limited. Insome cases, the synchronizer 122 receives multiple parameter files andmultiple recording files from various medical devices and recordingdevices. For example, the synchronizer 122 receives recorded parametersand audio recordings from multiple devices in a fleet associated with anEMS organization, which includes multiple rescuers responding to variousrescue scenes. The synchronizer 122 is configured to match a parameterfile with a corresponding recording file based on detecting audibleprompts in the recording file. For example, the synchronizer 122receives a first parameter file indicating an event in which a firstmedical device output a start-up sound and a defibrillation shock soundseparated by time period a, and also receives a second parameter fileindicating an event in which a second medical device output a start-upsound and a defibrillation shock sound separated by time period b,wherein a is different than b. The synchronizer 122 identifies thestart-up sounds and defibrillation shock sounds in a first recordingfile and a second recording file. By determining that the start-up soundand defibrillation shock sound in the first recording file are separatedby time period a, the synchronizer 122 determines that the firstrecording file is associated with the first parameter file (and not thesecond parameter file). Furthermore, by determining that the start-upsound and defibrillation shock in the second recording file areseparated by time period b, the synchronizer 122 determines that thesecond recording file is associated with the second parameter file (andnot the first parameter file). Thus, various implementations describedherein further enable the synchronizer 122 to match recorded parametersand audio recordings associated with the same events.

In some cases, the synchronizer 122 receives multiple parameter files118 and/or multiple recording 116 files obtained from a single rescuescene. For instance, the recording files 116 are obtained from multiplerecorders 114 in the rescue scene 102. The synchronizer aligns themultiple parameter files 118 and/or multiple recording files 116.According to some implementations, the synchronizer 122 generates thealigned data 124 to include the multiple parameter files 118 and/ormultiple recording files 116. The synchronizer 122, in variousinstances, combines the multiple recording files 116 into a single audiofile. The single audio file provides a surround-sound perspective of therescue scene when played by the playback device 126, in some cases.According to some implementations, the synchronizer 122 includes one ormore machine learning models configured to enhance a first recordingfile 116 based on a second recording file 116 and aligns the enhancedfirst recording file 116 with the parameter file 118. In some cases, thesynchronizer 122 removes noise or interference from the first recordingfile 116 based on the second recording file 116.

In various implementations, similar techniques to those described withrespect to FIG. 1 can be used to align a video file with the parameterfile 118. For example, the recording file 116 includes a video obtainedby the recorder 114 of the rescue scene 102. Instead of or in additionto the audible marker 112, the medical device 108 outputs a visualmarker that is depicted in the recording file 116 and indicated in theparameter file 118. The synchronizer 122, in various implementations,generates the aligned data 124 by time-aligning the recording file 116and the parameter file 118 based on detecting the audible marker 112and/or the visual marker in the recording file 116.

In various cases, the synchronizer 122 aligns parameter files 118generated by multiple medical devices 108. For instance, thesynchronizer 122 aligns parameter files 118 generated by a mechanicalchest compression device, a CPR sensor, a ventilator, a videolaryngoscope, an ultrasound imaging system, a cerebral oximeter, or someother type of monitor configured to detect a parameter of the patient106.

According to some implementations, the synchronizer 122 may detectvarious other features within the recording file 116. In some cases, themedical device 108 (e.g., a glucometer) outputs a sound encoding anumerical result of a parameter detected from the patient 106. Thesynchronizer 122, in some cases, identifies the numerical result byanalyzing the recording file 116, and includes the numerical result inthe report 128. In various cases, the medical device 108 outputs othersounds that are clinically relevant and captured in the recording file116. For example, a video laryngoscope makes a sound indicative of theapplication of force on the patient 106 during use, an infusion pumpgenerates a particular sound when it administers an intravenous drug tothe patient 106, or the like. The synchronizer 122 detects a soundoutput by the medical device 108 in the recording file 116 and indicatesthe associated clinically relevant information in the report 128, invarious cases. In some examples, the medical device 108 outputs a soundindicative of an identifier (e.g., a serial number) associated with thepatient 106 and/or the medical device 108, the synchronizer 122identifies the identifier based on the recording file 116, and indicatesthe identifier in the report 128 or verifies that the parameter file 118corresponds to the recording file 116 based on the identifier. In someimplementations, the synchronizer 122 identifies clinically relevantsounds output by the patient 106. For instance, the synchronizer 122detects agonal respirations (a sound made while in cardiac arrest,particularly early in the arrest, and is known to be associated withincreased patient viability or likelihood of survival) in the recordingfile 116 and indicates the agonal respirations in the report 128.

In some cases, the recorder 114 implements a “tap-to-talk”functionality. According to various implementations, the recorder 114 isconfigured to capture a short (e.g., a 5 second, 10 second, 30 second,etc.) audio recording in response to receiving an input signal from auser (e.g., the rescuer 104 presses a button of the recorder 114 or therescuer 104 taps a user interface element output on a touchscreen of therecorder 114). The rescuer 104 verbally announces an event during thecapture period of the recorder 114. In some cases, the short audiorecording is included in the recording file 116. The recorder 114provides the audio recording to the synchronizer 122. The synchronizer122 identifies the announced event (e.g., using speech-to-text) andincludes an indication of the announced event in the report 128. Invarious implementations, the synchronizer aligns the short audiorecording with the parameter file 118, such that the report 128indicates the announced event is also associated with one or moreparameters detected contemporaneously with the announced event at therescue scene 102.

In various implementations, a similar environment to the one illustratedin FIG. 1 can be used to synchronize video data captured by a camera ofthe recorder 114. For instance, the video data is at least a portion ofthe recording file 116, and is aligned with the parameter file 118 bythe synchronizer 122 using various techniques described herein. In somecases, a visible marker is used as an alternative (or in addition to)the audible marker 112 to align the parameter file 118 and the recordingfile 116. For instance, the medical device 108 includes a display, lightsource, or other output device configured to output a light-basedvisible marker to the recorder 114. For instance, the visible marker mayinclude an icon displayed by the medical device 108, a flashing-lightpattern output by the medical device 108, or the like. The recorder 114,in some implementations, further includes a camera and/or light sensorconfigured to detect the visible marker. The synchronizer 122 utilizesthe visible marker detected by the recorder 114 to align the parameterfile 118 and the recording file 116, for instance. In some cases, thevisible marker includes a light-based signal that imperceptible to therescuer 104 (e.g., the visible marker is output in a direction that doesnot intersect with the visual field of the rescuer 104, wherein thedirection may be different than a direction in which the medical device108 outputs a visual instruction to the rescuer 104). Accordingly, thevisible marker can be prevented from distracting the rescuer 104.

In some implementations, the recorder 114 is and/or includes anothermedical device configured to detect one or more additional parameters ofthe patient 106. For instance, the recorder 114 includes a mechanicalchest compression device, a CPR sensor (configured to detect manualchest compressions administered by the rescuer 104), a ventilator, avideo laryngoscope, a cerebral oximeter, an ultrasound imaging system,or a head-up CPR device. Various techniques described herein can be usedto align the parameter(s) detected by the medical device 108 withparameter(s) detected by the recorder 114.

In some cases, an additional device associated with the patient 106 isconfigured to output a sound that is detected by the recorder 114,wherein the sound itself encodes data relevant to managing care of thepatient 106. For instance, a glucometer detecting a level of glucose inthe blood of the patient 106 emits a sound that encodes the level of theglucose in the sound itself. The recorder 114 may indicate the time atwhich the sound was detected in the recording file 116, as well as anindication of the sound. The synchronizer 122 is configured to decodethe sound, thereby identifying the level of the glucose as well as thetime at which the level of the glucose was detected. In variousimplementations, the synchronizer 122 indicates the level of the glucosein the aligned data 124 and/or the report 128. Implementations are notlimited to glucometers and glucose levels, and can include any othersecondary medical device that detects a physiological parameter and/oradministers a therapy to the patient 106, wherein the sound emitted bythe secondary device encodes the physiological parameter and/or aparameter of the therapy. For example, a suction device and/or amechanical chest compression device may emit a sound indicating that achest compression is administered by the device, a force of the chestcompression administered by the device, a frequency of chestcompressions administered by the device, or a position of a chestcompression administered by the device. In particular cases, a videolaryngoscope emits a sound indicative of a force applied by the videolaryngoscope, which could be used to discern a time at which the patient106 is intubated (or a time at which individual intubation attemptsand/or events were performed). In some cases, an infusion pump emits asound indicative of a medication administered by the pump to the patient106.

In some implementations, the patient 106 is associated with a particularidentifier (e.g., a number uniquely associated with the patient 106 andnot other patients). In some cases, the medical device 108 generates theidentifier when the medical device 108 begins to monitor and/or treatthe patient 106. The audible marker 112, in some cases, encodes theidentifier. The recording file 116 may further indicate the identifierof the patient 106. The parameter file 118 may indicate the identifier.Accordingly, the synchronizer 122 may indicate the identifier in thealigned data 124 and/or the report 128. In some cases, the synchronizer122 determines that the recording file 116 and the parameter file 118are associated with the same patient 106 based on the identifier.

In some cases, the recorder 114 detects a sound from the patient 106 andindicates the sound in the recording file 116. For instance, therecorder 114 detects agonal respiration(s) of the patient 106. Agonalrespiration(s) may be associated with the patient 106 being in an earlystage of cardiac arrest. In some cases, the synchronizer 122 indicatesthe sound, or a condition associated with the sound, in the aligned data124 and/or the report 128. For instance, by identifying agonalrespiration(s), the care provider 120 may be enabled to treat thepatient 106 in the early stage of cardiac arrest, which can enhance theprognosis of the patient 106.

According to some examples, the medical device 108 emits the audiblemarker 112 multiple times during use. Thus, if the recorder 114 is notrecording ata particular time during the care event of the patient 106(e.g., when the medical device 108 is powered on), then the synchronizer122 may nevertheless align the recording file 116 and the parameter file118.

In various cases, the synchronizer 122 is configured to recognize anidentity of the rescuer 104 based on the voice of the rescuer 104indicated in the recording file 116. For instance, the synchronizer isconfigured to access a database storing voice parameters (e.g., spectralsignatures) of multiple rescuers in an EMS system. The synchronizer 122,in some cases, is configured to identify the rescuer 104 by comparing atleast a portion of the recording file 116 to the entries in thedatabase. In various cases, the synchronizer 122 indicates the identityof the rescuer 104 in the aligned data 124 and/or the report 128.

FIG. 2 illustrates an example of the parameter file 118 described abovewith reference to FIG. 1 . In FIG. 2 , time increases from left toright. The parameter file 118 includes two channels: a parameter channel202 and a marker channel 204. The parameter channel 202 includes valuesof a parameter, such as values of a physiological parameter of thepatient 106. The values of the parameter in the parameter channel 202are detected by the medical device 108 at a particular samplingfrequency, such as once a minute, five times a minute, 10 times aminute, 30 times a minute, once a second, or multiple times per second.That is, the values of the parameter in the parameter channel 202 aresampled at discrete (sampling) times. The values in the parameterchannel 202 are the sampled parameter values. Although various types ofparameters are possible in various implementations in the presentdisclosure, FIG. 2 illustrates an example of pulse oxygenation values ofthe patient 106 that are detected by the medical device 108 over aparticular time interval.

The marker channel 204 includes data indicating various audible markersoutput by the medical device 108 during the time interval. For instance,in the example of FIG. 2 , the medical device 108 outputs three audiblemarkers: audible marker “A,” audible marker “B,” and audible marker “C.”In various implementations, the parameter channel 202 and the markerchannel 204 are time-aligned, such that the parameter file 118 indicateswhat parameter values were detected as the audible markers were outputby the medical device 108. For example, the pulse oxygenation value ofthe patient 106 was “93” when audible marker “A” was output into therescue scene 102, the pulse oxygenation value of the patient 106 was“88” when audible marker “B” was output into the rescue scene 102, andthe pulse oxygenation value of the patient 106 was “85” when the audiblemarker “C” was output into the rescue scene 102. Although notillustrated in FIG. 2 , in some cases, the parameter file 118 furtherincludes a third channel indicating timestamps indicating when thevarious values of the parameter channel 202 were detected and theaudible markers of the marker channel 204 were output into the rescuescene 102.

FIG. 3 illustrates an example of the recording file 116 described abovewith reference to FIG. 1 . In FIG. 3 , time increases from left toright. In the example of FIG. 3 , the recording file 116 includes asingle channel: an audio recording 302. In some cases, the recordingfile 116 includes a second channel that includes timestamps aligned withthe audio recording 302. In cases where both the parameter file 118 andthe recording file 116 include timestamps, the timestamps of theparameter file 118 may be different than the timestamps in the recordingfile 116, because the parameter file 118 and the recording file 116 aregenerated by different devices that have different internal clocks anddo not communicate with each other.

As shown, the audio recording 302 includes discrete audio samples (D1 toD15) of sound in the rescue scene 102 taken at a particular samplingrate (i.e., at discrete times). The sampling rate of the recording file116 is, in some cases, different than the sampling rate of the parameterfile 118. In various implementations, the audio recording 302 includesdetected markers 304 in three respective audio samples: D9, D11, andD13. The three detected markers 304 correspond to the three audiblemarkers output by the medical device 108 and indicated in the markerchannel 204.

FIG. 4 illustrates an example of the aligned data 124 described abovewith reference to FIG. 1 . In FIG. 4 , time increases from left toright. The aligned data 124 includes two channels: the parameter channel202 of FIG. 2 and the audio recording 302 of FIG. 3 . For reference, themarker channel 304 is also depicted in FIG. 4 to show the alignmentbetween the parameter channel 202 and the audio recording 302.

Audible marker “A” is detected in audio sample D9, audible marker “B” isdetected in audio sample D11, and audible marker “C” is detected inaudio sample D13. Accordingly, audio sample D9 is aligned with theparameter value “93,” audio sample D11 is aligned with parameter value“88,” and audio sample D13 is aligned with parameter value “85.”Notably, the parameter channel 202 and the audio recording 302originally had different lengths. Accordingly, in some cases, the longerof the two (the audio recording 302) is edited to ensure that bothchannels in the aligned data 124 have the same length.

Although FIGS. 2-4 illustrate examples in which the parameter channel202, the marker channel 204, and the audio recording 302 are obtainedwith the same sampling rate, implementations are not so limited. Forexample, in examples in which the parameter channel 202 and the audiorecording have different sampling rates, they can nevertheless bealigned as long as their respective sampling rates are known. In somecases, the sampling rates are included in the parameter file 118 andrecording file 116, respectively. In some cases, the synchronizer 122infers the sampling rate of the parameter file 118 and/or the recordingfile 116 based on a file type of the parameter file 118 and/or recordingfile 116. For example, if the recording file 116 is an MP3 file, thesynchronizer 122 may infer that the recording file 116 has a samplingrate associated with the MP3 file format (e.g., 48 kHz).

FIG. 5 illustrates an example of the report 148 described above withreference to FIG. 1 . In various implementations, the report 148includes a patient identity 502, a rescuer identity 504, one or moreparameters 506, one or more treatments administered 508, andobservations at the rescue scene 510. In some cases, at least one of thepatient identity 502, the rescuer identity 504, the parameter(s) 506,the treatment(s) administered 508, and the observations at the rescuescene 510 is omitted from the report 148.

The patient identity 502 indicates a patient (e.g., the patient 106)being treated by a rescuer and/or medical device at a rescue scene. Insome examples, the patient identity 502 is uniquely specific to thepatient. For example, an EMS team treats multiple patients, but thepatient specified in the report 148 is the only patient with the patientidentity 502. In various cases, the patient identity 502 is a name ofthe patient, an identifier of the patient (e.g., a string and/or numberuniquely assigned to the patient), or one or more characteristics of thepatient (e.g., where the patient was found, demographic information ofthe patient, etc.). The patient identity 502 is input into the medicaldevice at the rescue scene, in various implementations. For example, therescuer inputs the patient identity 502 into the medical device at therescue scene.

The rescuer identity 504 indicates the rescuer (e.g., the rescuer 104)attending to the patient at the rescue scene. The rescuer identity 504is uniquely specific to the rescuer. For example, the EMS team includesmultiple rescuers, but only the rescuer attending to the patient has thespecific rescuer identity 504. In various cases, the rescuer identity504 is a name of the rescuer, an identifier of the patient (e.g., astring and/or number uniquely assigned to the rescuer). In someexamples, the rescuer identity 504 is input into the medical device bythe rescuer.

The parameter(s) 506 include one or more physiological parametersdetected from the patient at the rescue scene. In some cases, theparameter(s) 506 are detected by the medical device. In various cases,the parameter(s) 506 are derived based on the parameter file generatedby the medical device at the rescue scene. According to someimplementations, the parameter(s) 506 further specify the times at whichthe physiological parameter(s) are detected. For example, theparameter(s) 506 include timestamps indicating the times at which thephysiological parameter(s) were detected.

The treatment(s) administered 508 indicate one or more treatments of thepatient at the rescue scene. The treatment(s) are administered by therescuer, in some instances. For example, the treatment(s) administered508 indicate whether the patient was intubated, administered with amedication (e.g., a sedative, a paralytic, an antibiotic, etc.),defibrillated, or administered with any other type of treatment. Invarious cases, the treatment(s) administered 508 are input into themedical device by the rescuer at the rescue scene. In someimplementations, the treatment(s) administered 508 are identified basedon the voice of the rescuer in a recording file of the rescue scene(e.g., the recording file 116). For example, the rescuer verballyexplains that the patient is being intubated, a synchronizer (e.g., thesynchronizer 122) recognizes the words in the recording file indicatingthat the patient is being intubated (e.g., using speech-to-text), thesynchronizer recognizes the treatment based on the words (e.g., usingspeech recognition), and the synchronizer generates the treatment(s)administered 508 based on the recognized treatment. In someimplementations, the treatment(s) administered 508 further indicate thetime(s) at which the treatment(s) occurred. For instance, thesynchronizer identifies the time at which the patient is intubated basedon aligning the recording file with a parameter file and comparing therelative time at which the rescuer spoke the words indicating thetreatment in the recording file and the relative time at which parameterwas detected in the parameter file.

The observations at the rescue scene 510 indicate other informationabout the rescue scene. The observations at the rescue scene 510 areinput by the rescuer and/or derived (e.g., by the synchronizer) from thevoice of the rescuer in the recording file of the rescue scene. In somecases, the observations at the rescue scene 510 indicate a condition ofthe patient at the rescue scene (e.g., disoriented, unresponsive, etc.)or a result of a diagnostic test performed at the rescue scene (e.g., ablood glucose level of the patient measured at the rescue scene). Insome cases, the observations at the rescue scene 510 further indicatethe times at which the observations at the rescue scene 510 were made.

FIG. 6 illustrates an example rescue scene 600 associated with analternate technique for aligning a recording file and a parameter fileobtained by the medical device 108. As illustrated, the rescue scene 600further includes the rescuer 104, the patient 106, and the recorder 114described above with reference to FIG. 1 .

FIG. 6 further includes a satellite 602 that transmits at least onetiming signal 604 to the medical device 108 and to the recorder 114. Thesatellite 602, for example, is a device that is in the earth's orbit andconfigured to transmit signals to one or more receivers disposed on thesurface of the earth. The timing signal(s) 604 are transmittedwirelessly to the medical device 108 and to the recorder 114. Forexample, the timing signal(s) 604 are electromagnetic (e.g., radiofrequency) signals that encode information. The timing signal(s) arebroadcast from the satellite 602, for example. Although only a singlesatellite 602 is illustrated in FIG. 6 , in some cases, multiplesatellites including the satellite 602 transmit respective timingsignals to the medical device 108 and to the recorder 114.

The medical device 108 and the recorder 114 are independent computingdevices with respective receivers configured to receive the timingsignal(s) 604 and respective processors configured to analyze the timingsignal(s) 604. Based on information encoded in the timing signal(s) 604,the medical device 108 and the recorder 114 are able to recognize aconsistent time scale. Thus, when the medical device 108 generates aparameter file (e.g., the parameter file 118) and the recorder 114generates a recording file (e.g., the recording file 116), both theparameter file and the recording file can indicate a consistent timescale. In some cases, the parameter file includes timestamps and therecording file includes timestamps. Accordingly, a synchronizer (e.g.,the synchronizer 122) aligns the parameter file and the recording fileby matching or otherwise aligning the respective timestamps in theparameter file and the recording file.

In various implementations, the satellite 602 is part of a locationservice system. For example, the satellite 602 is a Global PositioningSystem (GPS) satellite and the timing signal(s) 604 are GPS signal(s).In some implementations, the satellite 602 is a Global NavigationSatellite System (GLONASS) satellite, a BeiDou Navigation satellite, aGalileo positioning system satellite, an Indian Regional NavigationSatellite System (IRNSS) satellite, or a Quasi-Zenith Satellite System(QZSS) satellite. In some examples, the satellite 602 is a Starlink™satellite. In particular cases, the satellite 602 is configured todetect its own position and the time at which the timing signal(s) 604are transmitted. The satellite 602 includes a time of transmission (TOT)of the timing signal(s) 604 in the timing signal(s) 604 themselves. Insome cases, the medical device 108 and the recorder 114 adopt the TOT ofthe timing signal(s) 604 as the times of arrival (TOAs) of the timingsignal(s) 604, even though the true TOAs would also be based on thetimes of flight (TOFs) of the timing signal(s) 604 and could be slightlydifferent between the medical device 108 and the recorder 114 based ontheir slight differences in location. In some cases, the medical device108 and the recorder 114 derive the true TOAs based on the TOTs of thetiming signal(s) 604. In some examples, the medical device 108 and therecorder generate the timestamps in the parameter file and the recordingfile based on the TOAs. For instance, the medical device 108 and therecorder 114 respectively calibrate their clocks based on the TOAs andgenerate the timestamps based on the calibrated clocks.

In particular examples, the medical device 108 or the recorder 114further determines its location based on the timing signal(s) 604. Forexample, the medical device 108 or the recorder 114 receives timingsignals 604 from multiple satellites 602 and may triangulate itsposition based on a discrepancy of the timing signals 604 from theindividual satellites 602. The medical device 108 or the recorder 114,in some cases, further transmits data indicative of its location to anexternal device (e.g., an external server) along with the recording fileand the parameter file. In various implementations, the external deviceanalyzes the recording file, the parameter file, and the location inaccordance with various implementations described herein.

FIG. 7 illustrates an example process 700 for aligning parameter dataand an audio recording. The process 700 is performed by an entity, suchas the synchronizer 122 described above with reference to FIG. 1 .

At 702, the entity receives, from a medical device, parameter data. Theparameter data indicates a physiological parameter of a patient, invarious implementations. For example, the parameter data includesdiscrete physiological parameter measurements detected at discretetimes, wherein the discrete times correspond to a sampling rate of themedical device. The parameter data indicates the physiological parametermeasurements in a first channel (e.g., a “parameter channel”). In somecases, the parameter data includes a second channel (e.g., a “markerchannel”) that indicates an audible marker output by the medical device.The second channel, for example, indicates the time and/or physiologicalparameter measurement detected when the audible marker is output by themedical device.

The entity receives the parameter data over a wireless and/or wiredinterface with the medical device. For instance, the medical deviceincludes a first transceiver and/or a transmitter configured to transmita signal indicative of the parameter data. The entity includes a secondtransceiver and/or a receive configured to receive the signal from themedical device. The medical device is, for example, amonitor-defibrillator.

At 704, the entity receives, from a recorder (also referred to as a“recording device”), an audio recording. The audio recording indicatesaudio sampled at an environment in which the patient was present as thephysiological parameter of the patient was detected. For instance, theaudio is sampled at a rescue scene in which a rescuer is monitoringand/or treating the patient with the medical device. The audiorecording, in some implementations, includes audio sampled at discretetimes corresponding to a sampling rate of the recorder. In variousexamples, the sampling rate of the recorder is different than thesampling rate of the medical device. The sound of the audible markeroutput by the medical device is indicated in the audio recording, invarious cases.

The entity receives the audio recording over a wireless and/or wiredinterface with the recorder. For example, the recorder includes a thirdtransceiver and/or a transmitter configured to transmit a signalindicative of the audio recording. The entity is configured to receivethe signal from the recorder. In various implementations, the recorderis separate from the medical device. For instance, the recorder isincapable of communicating directly with the medical device. In variouscases, the recorder includes a mobile device or a standalone recordingdevice.

At 706, the entity generates aligned data by time-aligning the parameterdata and the audio record. In various implementations, the entityidentifies the sound of the audible marker in the audio recording. Basedon identifying the audible marker, the entity generates aligned data bytime-aligning the detected physiological parameter measurements and theaudio recording. For example, the entity aligns the physiologicalparameter measurement taken simultaneously as the audible marker wasoutput by the medical device with the audio sample including the soundof the audible marker. The aligned data, in various cases, includes twochannels: a first channel including the physiological parametermeasurements and a second channel including the audio recording.

In particular implementations, the entity further performs additionalactions based on the aligned data. In some cases, the entity outputs thealigned data. For example, the entity includes a screen that visuallyoutputs a waveform representing the physiological parameter measurementsand a speaker that audibly outputs the audio recording. In someexamples, the entity transmits a signal indicative of the aligned datato an external device, which outputs the aligned data.

According to some cases, the entity generates a report based on theparameter data, the audio recording, the aligned data, or a combinationthereof. In some implementations, the entity recognizes one or morewords spoken by a rescuer in the audio recording, identifies an eventbased on the word(s), and indicates the event in the report. Forinstance, the entity identifies words indicating that the rescuer hasintubated the patient, and indicates that the patient was intubated inthe report. In some examples, the entity further indicates a time (e.g.,a time relative to the physiological parameter measurements and/or audiorecording) at which the event occurred. In some implementations, theentity indicates further identifying information about the patientand/or rescuer in the report. The entity outputs the report and/ortransmits a signal indicative of the report to an external device.

FIG. 8 illustrates an example of an external defibrillator 800configured to perform various functions described herein. For example,the external defibrillator 800 is the medical device 106 described abovewith reference to FIG. 1 .

The external defibrillator 800 includes an electrocardiogram (ECG) port802 connected to multiple ECG leads 804. In some cases, the ECG leads804 are removeable from the ECG port 802. For instance, the ECG leads804 are plugged into the ECG port 802. The ECG leads 804 are connectedto ECG electrodes 806, respectively. In various implementations, the ECGelectrodes 806 are disposed on different locations on an individual 808.A detection circuit 810 is configured to detect relative voltagesbetween the ECG electrodes 806. These voltages are indicative of theelectrical activity of the heart of the individual 808.

In various implementations, the ECG electrodes 806 are in contact withthe different locations on the skin of the individual 808. In someexamples, a first one of the ECG electrodes 806 is placed on the skinbetween the heart and right arm of the individual 808, a second one ofthe ECG electrodes 806 is placed on the skin between the heart and leftarm of the individual 808, and a third one of the ECG electrodes 806 isplaced on the skin between the heart and a leg (either the left leg orthe right leg) of the individual 808. In these examples, the detectioncircuit 808 is configured to measure the relative voltages between thefirst, second, and third ECG electrodes 806. Respective pairings of theECG electrodes 806 are referred to as “leads,” and the voltages betweenthe pairs of ECG electrodes 806 are known as “lead voltages.” In someexamples, more than three ECG electrodes 806 are included, such that5-lead or 12-lead ECG signals are detected by the detection circuit 810.

The detection circuit 810 includes at least one analog circuit, at leastone digital circuit, or a combination thereof. The detection circuit 810receives the analog electrical signals from the ECG electrodes 806, viathe ECG port 802 and the ECG leads 804. In some cases, the detectioncircuit 810 includes one or more analog filters configured to filternoise and/or artifact from the electrical signals. The detection circuit810 includes an analog-to-digital (ADC) in various examples. Thedetection circuit 810 generates a digital signal indicative of theanalog electrical signals from the ECG electrodes 806. This digitalsignal can be referred to as an “ECG signal” or an “ECG.”

In some cases, the detection circuit 810 further detects an electricalimpedance between at least one pair of the ECG electrodes 806. Forexample, the detection circuit 810 includes, or otherwise controls, apower source that applies a known voltage across a pair of the ECGelectrodes 806 and detects a resultant current between the pair of theECG electrodes 806. The impedance is generated based on the appliedvoltage and the resultant current. In various cases, the impedancecorresponds to respiration of the individual 808, chest compressionsperformed on the individual 808, and other physiological states of theindividual 808. In various examples, the detection circuit 810 includesone or more analog filters configured to filter noise and/or artifactfrom the resultant current. The detection circuit 810 generates adigital signal indicative of the impedance using an ADC. This digitalsignal can be referred to as an “impedance signal” or an “impedance.”

The detection circuit 810 provides the ECG signal and/or the impedancesignal one or more processors 812 in the external defibrillator 800. Insome implementations, the processor(s) 812 includes a central processingunit (CPU), a graphics processing unit (GPU), both CPU and GPU, or otherprocessing unit or component known in the art.

The processor(s) 812 is operably connected to memory 814. In variousimplementations, the memory 812 is volatile (such as random accessmemory (RAM)), non-volatile (such as read only memory (ROM), flashmemory, etc.) or some combination of the two. The memory 814 storesinstructions that, when executed by the processor(s) 812, causes theprocessor(s) 812 to perform various operations. In various examples, thememory 814 stores methods, threads, processes, applications, objects,modules, any other sort of executable instruction, or a combinationthereof. In some cases, the memory 814 stores files, databases, or acombination thereof. In some examples, the memory 814 includes, but isnot limited to, RAM, ROM, electrically erasable programmable read-onlymemory (EEPROM), flash memory, or any other memory technology. In someexamples, the memory 814 includes one or more of CD-ROMs, digitalversatile discs (DVDs), content-addressable memory (CAM), or otheroptical storage, magnetic cassettes, magnetic tape, magnetic diskstorage or other magnetic storage devices, or any other medium which canbe used to store the desired information and which can be accessed bythe processor(s) 812 and/or the external defibrillator 800. In somecases, the memory 814 at least temporarily stores the ECG signal and/orthe impedance signal.

In various examples, the memory 814 includes a detector 816, whichcauses the processor(s) 812 to determine, based on the ECG signal and/orthe impedance signal, whether the individual 808 is exhibiting aparticular heart rhythm. For instance, the processor(s) 812 determineswhether the individual 808 is experiencing a shockable rhythm that istreatable by defibrillation. Examples of shockable rhythms includeventricular fibrillation (VF) and ventricular tachycardia (V-Tach). Insome examples, the processor(s) 812 determines whether any of a varietyof different rhythms (e.g., asystole, sinus rhythm, atrial fibrillation(AF), etc.) are present in the ECG signal.

The processor(s) 812 is operably connected to one or more input devices818 and one or more output devices 820. Collectively, the inputdevice(s) 818 and the output device(s) 820 function as an interfacebetween a user and the defibrillator 800. The input device(s) 818 isconfigured to receive an input from a user and includes at least one ofa keypad, a cursor control, a touch-sensitive display, a voice inputdevice (e.g., a speaker), a haptic feedback device, or any combinationthereof. The output device(s) 820 includes at least one of a display, aspeaker, a haptic output device, a printer, or any combination thereof.In various examples, the processor(s) 812 causes a display among theinput device(s) 818 to visually output a waveform of the ECG signaland/or the impedance signal. In some implementations, the inputdevice(s) 818 includes one or more touch sensors, the output device(s)820 includes a display screen, and the touch sensor(s) are integratedwith the display screen. Thus, in some cases, the external defibrillator800 includes a touchscreen configured to receive user input signal(s)and visually output physiological parameters, such as the ECG signaland/or the impedance signal.

In some examples, the memory 814 includes an advisor 822, which, whenexecuted by the processor(s) 812, causes the processor(s) 812 togenerate advice and/or control the output device(s) 820 to output theadvice to a user (e.g., a rescuer). In some examples, the processor(s)812 provides, or causes the output device(s) 820 to provide, aninstruction to perform CPR on the individual 808. In some cases, theprocessor(s) 812 evaluates, based on the ECG signal, the impedancesignal, or other physiological parameters, CPR being performed on theindividual 808 and causes the output device(s) 820 to provide feedbackabout the CPR in the instruction. According to some examples, theprocessor(s) 812, upon identifying that a shockable rhythm is present inthe ECG signal, causes the output device(s) 820 to output an instructionand/or recommendation to administer a defibrillation shock to theindividual 808.

The memory 814 also includes an initiator 824 which, when executed bythe processor(s) 812, causes the processor(s) 812 to control otherelements of the external defibrillator 800 in order to administer adefibrillation shock to the individual 808. In some examples, theprocessor(s) 812 executing the initiator 824 selectively causes theadministration of the defibrillation shock based on determining that theindividual 808 is exhibiting the shockable rhythm and/or based on aninput from a user (received, e.g., by the input device(s) 818. In somecases, the processor(s) 812 causes the defibrillation shock to be outputat a particular time, which is determined by the processor(s) 812 basedon the ECG signal and/or the impedance signal.

The processor(s) 812 is operably connected to a charging circuit 823 anda discharge circuit 825. In various implementations, the chargingcircuit 823 includes a power source 826, one or more charging switches828, and one or more capacitors 830. The power source 826 includes, forinstance, a battery. The processor(s) 812 initiates a defibrillationshock by causing the power source 826 to charge at least one capacitoramong the capacitor(s) 830. For example, the processor(s) 812 activatesat least one of the charging switch(es) 828 in the charging circuit 823to complete a first circuit connecting the power source 826 and thecapacitor to be charged. Then, the processor(s) 812 causes the dischargecircuit 825 to discharge energy stored in the charged capacitor across apair of defibrillation electrodes 830, which are in contact with theindividual 808. For example, the processor(s) 812 deactivates thecharging switch(es) 828 completing the first circuit between thecapacitor(s) 830 and the power source 826, and activates one or moredischarge switches 832 completing a second circuit connecting thecharged capacitor 830 and at least a portion of the individual 808disposed between defibrillation electrodes 834.

The energy is discharged from the defibrillation electrodes 834 in theform of a defibrillation shock. For example, the defibrillationelectrodes 834 are connected to the skin of the individual 808 andlocated at positions on different sides of the heart of the individual808, such that the defibrillation shock is applied across the heart ofthe individual 808. The defibrillation shock, in various examples,depolarizes a significant number of heart cells in a short amount oftime. The defibrillation shock, for example, interrupts the propagationof the shockable rhythm (e.g., VF or V-Tach) through the heart. In someexamples, the defibrillation shock is 200 J or greater with a durationof about 0.015 seconds. In some cases, the defibrillation shock has amultiphasic (e.g., biphasic) waveform. The discharge switch(es) 832 arecontrolled by the processor(s) 812, for example. In variousimplementations, the defibrillation electrodes 834 are connected todefibrillation leads 836. The defibrillation leads 836 are connected toa defibrillation port 838, in implementations. According to variousexamples, the defibrillation leads 836 are removable from thedefibrillation port 838. For example, the defibrillation leads 836 areplugged into the defibrillation port 838.

In various implementations, the processor(s) 812 is operably connectedto one or more transceivers 840 that transmit and/or receive data overone or more communication networks 842. For example, the transceiver(s)840 includes a network interface card (NIC), a network adapter, a localarea network (LAN) adapter, or a physical, virtual, or logical addressto connect to the various external devices and/or systems. In variousexamples, the transceiver(s) 840 includes any sort of wirelesstransceivers capable of engaging in wireless communication (e.g., radiofrequency (RF) communication). For example, the communication network(s)842 includes one or more wireless networks that include a 3^(rd)Generation Partnership Project (3GPP) network, such as a Long TermEvolution (LTE) radio access network (RAN) (e.g., over one or more LEbands), a New Radio (NR) RAN (e.g., over one or more NR bands), or acombination thereof. In some cases, the transceiver(s) 840 includesother wireless modems, such as a modem for engaging in WI-FI®, WIGIG®,WIMAX®, BLUETOOTH®, or infrared communication over the communicationnetwork(s) 842.

The defibrillator 800 is configured to transmit and/or receive data(e.g., ECG data, impedance data, data indicative of one or more detectedheart rhythms of the individual 808, data indicative of one or moredefibrillation shocks administered to the individual 808, etc.) with oneor more external devices 844 via the communication network(s) 842. Theexternal devices 844 include, for instance, mobile devices (e.g., mobilephones, smart watches, etc.), Internet of Things (loT) devices, medicaldevices, computers (e.g., laptop devices, servers, etc.), or any othertype of computing device configured to communicate over thecommunication network(s) 842. In some examples, the external device(s)844 is located remotely from the defibrillator 800, such as at a remoteclinical environment (e.g., a hospital). According to variousimplementations, the processor(s) 812 causes the transceiver(s) 840 totransmit data (e.g., a parameter file) to the external device(s) 844. Insome cases, the transceiver(s) 840 receives data from the externaldevice(s) 844 and the transceiver(s) 840 provide the received data tothe processor(s) 812 for further analysis. In some implementations, theexternal device(s) 884 include a recording device and a synchronizer.For example, the synchronizer receives the data from the defibrillator800 and time-aligns the data with an audio recording detected by therecording device. Although not specifically illustrated in FIG. 8 , eachone of the external devices 884 includes a processor configured toperform operations and a memory storing instructions for performing theoperations.

In various implementations, the external defibrillator 800 also includesa housing 846 that at least partially encloses other elements of theexternal defibrillator 800. For example, the housing 846 encloses thedetection circuit 810, the processor(s) 812, the memory 814, thecharging circuit 823, the transceiver(s) 840, or any combinationthereof. In some cases, the input device(s) 818 and output device(s) 820extend from an interior space at least partially surrounded by thehousing 846 through a wall of the housing 846. In various examples, thehousing 846 acts as a barrier to moisture, electrical interference,and/or dust, thereby protecting various components in the externaldefibrillator 800 from damage.

In some implementations, the external defibrillator 800 is an automatedexternal defibrillator (AED) operated by an untrained user (e.g., abystander, layperson, etc.) and can be operated in an automatic mode. Inautomatic mode, the processor(s) 812 automatically identifies a rhythmin the ECG signal, makes a decision whether to administer adefibrillation shock, charges the capacitor(s) 830, discharges thecapacitor(s) 830, or any combination thereof. In some cases, theprocessor(s) 812 controls the output device(s) 820 to output (e.g.,display) a simplified user interface to the untrained user. For example,the processor(s) 812 refrains from causing the output device(s) 820 todisplay a waveform of the ECG signal and/or the impedance signal to theuntrained user, in order to simplify operation of the externaldefibrillator 800.

In some examples, the external defibrillator 800 is amonitor-defibrillator utilized by a trained user (e.g., a clinician, anemergency responder, etc.) and can be operated in a manual mode or theautomatic mode. When the external defibrillator 800 operates in manualmode, the processor(s) 812 cause the output device(s) 820 to display avariety of information that may be relevant to the trained user, such aswaveforms indicating the ECG data and/or impedance data, notificationsabout detected heart rhythms, and the like.

EXAMPLE CLAUSES

-   -   1. A system including: a defibrillator including: a sensor        configured to detect values of a physiological parameter of a        patient in an environment at discrete times in a time interval;        a speaker configured to output an audible marker into the        environment at a particular time among the discrete times; a        first processor configured to generate monitor data including: a        parameter channel indicating the physiological parameter at the        discrete times; and a marker channel indicating the audible        marker output at the particular time; and a first transceiver        configured to transmit the monitor data; and a synchronizer        including: a second transceiver configured to receive the        monitor data from the defibrillator and to receive recorder data        from a recording device, the recorder data being indicative of        an audio recording of the environment during the time interval;        a second processor configured to: detect the audible marker in        the audio recording; and generate aligned data by aligning the        parameter channel and the audio recording based on the audible        marker indicated in the marker channel and detected in the audio        recording; and an output device configured to output the aligned        data.    -   2. The system of clause 1, wherein the second processor is        further configured to: identify words spoken by a rescuer by        performing speech-to-text on an additional sound in the audio        recording; and generate a record associated with the patient        based on the words.    -   3. The system of clause 1 or 2, wherein the recording device        includes a mobile phone or a wearable device.    -   4. A synchronizer, including: a receiver configured to: receive        monitor data from a medical device, the monitor data indicating        a physiological parameter of a patient detected by the medical        device during a time interval and a marker output by the medical        device into an environment during the time interval; and receive        recording data from a recording device, the recording data        including an audio recording of the environment during the time        interval; a processor; and memory storing instructions that,        when executed by the processor, cause the processor to perform        operations including: identifying the marker in the audio        recording of the environment; and based on identifying the        marker in the audio recording of the environment, generating        aligned data by time-aligning the physiological parameter of the        patient and the audio recording.    -   5. The synchronizer of clause 4, further including: an output        device configured to output the aligned data.    -   6. The synchronizer of clause 5, wherein the output device        includes a screen and a speaker and is configured to output the        aligned data by simultaneously: displaying, on the screen, an        animation of a waveform of the physiological parameter; and        outputting, by the speaker, the audio recording of the        environment.    -   7. The synchronizer of any one of clauses 4 to 6, wherein the        operations further include: identifying a voice notation in the        audio recording of the environment; determining, based on the        aligned data, a discrete time in the time interval when the        voice notation occurred; and generating a record associated with        the patient, the record indicating the voice notation and the        discrete time when the voice notation occurred.    -   8. The synchronizer of clause 7, wherein identifying the voice        notation includes determining that a rescuer has administered a        treatment to the patient by performing speech-to-text on the        audio recording, and wherein the record further indicates the        treatment administered to the patient.    -   9. The synchronizer of any one of clauses 4 to 8, wherein the        marker includes a power up sound of the medical device, a power        off sound of the medical device, an audible instruction output        by the medical device, or an alarm output by the medical device.    -   10. The synchronizer of any one of clauses 4 to 9, wherein the        medical device includes a defibrillator, an ultrasound device,        or a ventilation device.    -   11. The synchronizer of any one of clauses 4 to 10, wherein the        physiological parameter includes an electrocardiogram (ECG), an        oxygenation of the patient's blood, an amount of carbon dioxide        in the patient's breath, a heart rate of the patient, a blood        pressure of the patient, a carboxyhemoglobin level of the        patient's blood, a temperature of the patient, a respiration        rate of the patient, or a pulse rate of the patient.    -   12. The synchronizer of any one of clauses 4 to 11, wherein the        recorder device includes a mobile device or a wearable device.    -   13. A method, including: receiving, from a first device, a first        file including first measurements of a first parameter at first        discrete times in a time interval, the first file further        including a marker output by the first device during the time        interval; receiving, from a second device, a second file        including second measurements of a second parameter at second        discrete times in the time interval; detecting the marker output        by the first device in the second measurements of the second        parameter; based on detecting the signal output by the first        device in the second measurements, generating aligned data by        time-aligning the first measurements of the first parameter and        the second measurements of the second parameter; and outputting        the aligned data.    -   14. The method of clause 13, wherein the first device includes a        defibrillator and the second device includes a mobile device or        a wearable device.    -   15. The method of clause 13 or 14, wherein the first parameter        includes an electrocardiogram (ECG) of a patient, an oxygenation        of the patient's blood, an amount of carbon dioxide in the        patient's breath, a heart rate of the patient, a blood pressure        of the patient, a carboxyhemoglobin level of the patient's        blood, a temperature of the patient, a respiration rate of the        patient, or a pulse rate of the patient, and wherein the second        parameter includes sound, the second measurements including an        audio recording.    -   16. The method of clause 15, wherein the marker includes a power        up sound of the first device, a power off sound of the first        device, an audible instruction output by the first device, or an        alarm output by the first device.    -   17. The method of clause 15 or 16, wherein outputting the        aligned data includes simultaneously: displaying, on a screen,        an animation of a waveform of the first parameter; and        outputting, by a speaker, the audio recording.    -   18. The method of any one of clauses 15 to 17, further        including: identifying words by performing speech-to-text on the        audio recording; and generating a record including the words and        the first measurements of the first parameter.    -   19. The method of clause 18, further including: determining that        a treatment has been administered to a patient based on the        words, wherein the record indicates the treatment administered        to the patient.    -   20. The method of clause 18 or 19, further including:        transmitting the record to an external computing device.    -   21. A synchronizer, including: a receiver configured to:        receive, from medical devices, parameter files, the parameter        files respectively including first channels indicating        physiological parameters of patients detected by the medical        devices during time intervals and second channels indicating        audible markers output by the medical devices during the time        intervals; and receive, from recording devices, recording files,        the recording files including audio recordings by the recording        devices; a processor; and memory storing instructions that, when        executed by the processor, cause the processor to perform        operations including: selecting a particular parameter file        among the parameter files received from a particular medical        device among the medical devices, the first channel of the        particular medical device indicating a physiological parameter        of a particular patient among the patients detected during a        particular time interval among the time intervals, the second        channel of the parameter file indicating a first audible marker        output by the particular medical device in the time interval and        a second audible marker output by the medical device in the time        interval; identifying a time difference between the first        audible marker output by the particular medical device and the        second audible marker output by the particular medical device;        identifying a set of recording files among the recording files        that include audio recordings of the first audible marker and        the second audible marker; identifying a particular recording        file among the set of recording files indicating the first        audible marker and the second audible marker separated by the        time difference; and generating aligned data by time-aligning        the first channel of the particular parameter file and the        particular recording file.    -   22. The synchronizer of clause 21, wherein the medical devices        include defibrillators, and the physiological parameters include        electrocardiograms (ECG) of the patients, oxygenations of the        patients' blood, amounts of carbon dioxide in the patients'        breath, heart rates of the patients, blood pressures of the        patients, carboxyhemoglobin levels of the patients' blood,        temperatures of the patients, respiration rates of the patients,        or pulse rates of the patients.    -   23. The synchronizer of clause 21 or 22, wherein the recording        devices include mobile devices or wearable devices.    -   24. The synchronizer of any one of clauses 21 to 23, wherein the        first audible marker or the second audible marker includes a        power up sound of the particular medical device, a power off        sound of the particular medical device, an audible instruction        output by the particular medical device, or an audible alarm        output by the particular medical device.    -   25. The synchronizer of any one of clauses 21 to 24, further        including: an output device configured to output the aligned        data.    -   26. A method including: receiving, from medical devices,        parameter files, the parameter files respectively including        first channels indicating physiological parameters of patients        detected by the medical devices during time intervals and second        channels indicating audible markers output by the medical        devices during the time intervals; receiving, from recording        devices, recording files, the recording files including audio        recordings by the recording devices; selecting a particular        parameter file among the parameter files received from a        particular medical device among the medical devices, the first        channel of the particular medical device indicating a        physiological parameter of a particular patient among the        patients detected during a particular time interval among the        time intervals, the second channel of the parameter file        indicating a first audible marker output by the particular        medical device in the time interval and a second audible marker        output by the medical device in the time interval; identifying a        time difference between the first audible marker output by the        particular medical device and the second audible marker output        by the particular medical device; identifying a set of recording        files among the recording files that include audio recordings of        the first audible marker and the second audible marker;        identifying a particular recording file among the set of        recording files indicating the first audible marker and the        second audible marker separated by the time difference; and        generating aligned data by time-aligning the first channel of        the particular parameter file and the particular recording file.    -   27. The method of clause 26, wherein the medical devices include        defibrillators, and the physiological parameters include        electrocardiograms (ECG) of the patients, oxygenations of the        patients' blood, amounts of carbon dioxide in the patients'        breath, heart rates of the patients, blood pressures of the        patients, carboxyhemoglobin levels of the patients' blood,        temperatures of the patients, respiration rates of the patients,        or pulse rates of the patients.    -   28. The method of clause 26 or 27, wherein the recording devices        include mobile devices or wearable devices.    -   29. The method of any one of clauses 26 to 28, wherein the first        audible marker or the second audible marker includes a power up        sound of the particular medical device, a power off sound of the        particular medical device, an audible instruction output by the        particular medical device, or an audible alarm output by the        particular medical device.    -   30. The method one of clauses 26 to 29, further including:        outputting the aligned data.    -   31. The method of one of clauses 26 to 30, further including:        identifying words in the particular recording file; generating a        record associated with the particular patient based on the        words; and transmitting the record to an external computing        device.    -   32. The method of clause 31, further including: determining that        the words in the particular recording file indicate a treatment        administered to the patient during the time interval, wherein        the record further indicates the treatment administered to the        patient during the time interval.    -   33. A system including: a medical device including: a receiver        configured to receive timing signals from satellites; a sensor        configured to detect values of a physiological parameter of a        patient at discrete times during a time interval; a processor        configured to: identify the discrete times based on the timing        signals; and generate a parameter file including a first channel        and a second channel, the first channel including the        physiological parameter of the patient and the second channel        including the discrete times; and a synchronizer including: a        receiver configured to: receive the parameter file from the        medical device; receive, from a recording device, a recording        file including a third channel indicating an audio recording        detected by the recording device during the time interval and a        fourth channel indicating the discrete times; a processor; and        memory storing instructions that, when executed by the        processor, cause the processor to perform operations including:        generating aligned data by time-aligning the first channel and        the third channel based on the discrete times indicated in the        second channel and the fourth channel; and an output device        configured to output the aligned data.    -   34. The system of clause 33, wherein the output device includes        a screen and a speaker and is configured to output the aligned        data by simultaneously: displaying, on the screen, an animation        of a waveform of the physiological parameter; and outputting, by        the speaker, the audio recording.    -   35. The system of clause 33 or 34, wherein the operations        further include: identifying a voice notation in the audio        recording; determining, based on the aligned data, a discrete        time in the time interval when the voice notation occurred; and        generating a record associated with the patient, the record        indicating the voice notation and the discrete time when the        voice notation occurred.    -   36. The system of clause 35, wherein identifying the voice        notation includes determining that a rescuer has administered a        treatment to the patient by performing speech-to-text on the        audio recording, and wherein the record further indicates the        treatment administered to the patient.    -   37. The system of any one of clauses 33 to 36, wherein the        medical device includes a defibrillator.    -   38. The system of any one of clauses 33 to 37, wherein the        physiological parameter includes an electrocardiogram (ECG), an        oxygenation of the patient's blood, an amount of carbon dioxide        in the patient's breath, a heart rate of the patient, a blood        pressure of the patient, a carboxyhemoglobin level of the        patient's blood, a temperature of the patient, a respiration        rate of the patient, or a pulse rate of the patient.    -   39. The system of any one of clauses 33 to 38, wherein the        recorder device includes a mobile device or a wearable device.    -   40. A method, including: identifying a first file including        first measurements of a first parameter at first discrete times        in a time interval, the first file further including a marker        output by the first device during the time interval; identifying        a second file including second measurements of a second        parameter at second discrete times in the time interval;        detecting the marker output by the first device in the second        measurements of the second parameter; and based on detecting the        signal output by the first device in the second measurements,        generating aligned data by time-aligning the first measurements        of the first parameter and the second measurements of the second        parameter.    -   41. The method of clause 40, wherein the first file and the        second file are generated by different devices.    -   42. The method of clause 40 or 41, wherein the operations        further include: outputting the aligned data.

The features disclosed in the foregoing description, or the followingclaims, or the accompanying drawings, expressed in their specific formsor in terms of a means for performing the disclosed function, or amethod or process for attaining the disclosed result, as appropriate,may, separately, or in any combination of such features, be used forrealizing implementations of the disclosure in diverse forms thereof.

As will be understood by one of ordinary skill in the art, eachimplementation disclosed herein can comprise, consist essentially of orconsist of its particular stated element, step, or component. Thus, theterms “include” or “including” should be interpreted to recite:“comprise, consist of, or consist essentially of.” The transition term“comprise” or “comprises” means has, but is not limited to, and allowsfor the inclusion of unspecified elements, steps, ingredients, orcomponents, even in major amounts. The transitional phrase “consistingof” excludes any element, step, ingredient or component not specified.The transition phrase “consisting essentially of” limits the scope ofthe implementation to the specified elements, steps, ingredients orcomponents and to those that do not materially affect theimplementation. As used herein, the term “based on” is equivalent to“based at least partly on,” unless otherwise specified. The term “beingindicative of” may refer to something that indicates or otherwise showsanother feature.

Unless otherwise indicated, all numbers expressing quantities,properties, conditions, and so forth used in the specification andclaims are to be understood as being modified in all instances by theterm “about.” Accordingly, unless indicated to the contrary, thenumerical parameters set forth in the specification and attached claimsare approximations that may vary depending upon the desired propertiessought to be obtained by the present disclosure. At the very least, andnot as an attempt to limit the application of the doctrine ofequivalents to the scope of the claims, each numerical parameter shouldat least be construed in light of the number of reported significantdigits and by applying ordinary rounding techniques. When furtherclarity is required, the term “about” has the meaning reasonablyascribed to it by a person skilled in the art when used in conjunctionwith a stated numerical value or range, i.e. denoting somewhat more orsomewhat less than the stated value or range, to within a range of ±20%of the stated value; ±19% of the stated value; ±18% of the stated value;±17% of the stated value; ±16% of the stated value; ±15% of the statedvalue; ±14% of the stated value; ±13% of the stated value; ±12% of thestated value; ±11% of the stated value; ±10% of the stated value; ±9% ofthe stated value; ±8% of the stated value; ±7% of the stated value; ±6%of the stated value; ±5% of the stated value; ±4% of the stated value;±3% of the stated value; ±2% of the stated value; or ±1% of the statedvalue.

Notwithstanding that the numerical ranges and parameters setting forththe broad scope of the disclosure are approximations, the numericalvalues set forth in the specific examples are reported as precisely aspossible. Any numerical value, however, inherently contains certainerrors necessarily resulting from the standard deviation found in theirrespective testing measurements.

The terms “a,” “an,” “the” and similar referents used in the context ofdescribing implementations (especially in the context of the followingclaims) are to be construed to cover both the singular and the plural,unless otherwise indicated herein or clearly contradicted by context.Recitation of ranges of values herein is merely intended to serve as ashorthand method of referring individually to each separate valuefalling within the range. Unless otherwise indicated herein, eachindividual value is incorporated into the specification as if it wereindividually recited herein. All methods described herein can beperformed in any suitable order unless otherwise indicated herein orotherwise clearly contradicted by context. The use of any and allexamples, or exemplary language (e.g., “such as”) provided herein isintended merely to better illuminate implementations of the disclosureand does not pose a limitation on the scope of the disclosure. Nolanguage in the specification should be construed as indicating anynon-claimed element essential to the practice of implementations of thedisclosure.

Groupings of alternative elements or implementations disclosed hereinare not to be construed as limitations. Each group member may bereferred to and claimed individually or in any combination with othermembers of the group or other elements found herein. It is anticipatedthat one or more members of a group may be included in, or deleted from,a group for reasons of convenience and/or patentability. When any suchinclusion or deletion occurs, the specification is deemed to contain thegroup as modified thus fulfilling the written description of all Markushgroups used in the appended claims.

Certain implementations are described herein, including the best modeknown to the inventors for carrying out implementations of thedisclosure. Of course, variations on these described implementationswill become apparent to those of ordinary skill in the art upon readingthe foregoing description. The inventor expects skilled artisans toemploy such variations as appropriate, and the inventors intend forimplementations to be practiced otherwise than specifically describedherein. Accordingly, the scope of this disclosure includes allmodifications and equivalents of the subject matter recited in theclaims appended hereto as permitted by applicable law. Moreover, anycombination of the above-described elements in all possible variationsthereof is encompassed by implementations of the disclosure unlessotherwise indicated herein or otherwise clearly contradicted by context.

What is claimed is:
 1. A system comprising: a defibrillator comprising:a sensor configured to detect values of a physiological parameter of apatient in an environment at discrete times in a time interval; aspeaker configured to output an audible marker into the environment at aparticular time among the discrete times; a first processor configuredto generate monitor data comprising: a parameter channel indicating thevalues of the physiological parameter at the discrete times; and amarker channel indicating the audible marker output at the particulartime; and a first transceiver configured to transmit the monitor data;and a synchronizer comprising: a second transceiver configured toreceive the monitor data from the defibrillator and to receive recorderdata from a recording device, the recorder data being indicative of anaudio recording of the environment during the time interval; a secondprocessor configured to: detect the audible marker in the audiorecording; and generate aligned data by aligning the parameter channeland the audio recording based on the audible marker indicated in themarker channel and detected in the audio recording; and an output deviceconfigured to output the aligned data.
 2. The system of claim 1, whereinthe second processor is further configured to: identify words spoken bya rescuer by performing speech-to-text on an additional sound in theaudio recording; and generate a record associated with the patient basedon the words.
 3. The system of claim 1, wherein the recording devicecomprises a mobile phone or a wearable device.
 4. A synchronizer,comprising: a receiver configured to: receive monitor data from amedical device, the monitor data indicating a physiological parameter ofa patient detected by the medical device during a time interval and amarker output by the medical device into an environment during the timeinterval; and receive recording data from a recording device, therecording data comprising an audio recording of the environment duringthe time interval; a processor; and memory storing instructions that,when executed by the processor, cause the processor to performoperations comprising: identifying the marker in the audio recording ofthe environment; and based on identifying the marker in the audiorecording of the environment, generating aligned data by time-aligningthe physiological parameter of the patient and the audio recording. 5.The synchronizer of claim 4, further comprising: an output deviceconfigured to output the aligned data.
 6. The synchronizer of claim 5,wherein the output device comprises a screen and a speaker and isconfigured to output the aligned data by simultaneously: displaying, onthe screen, an animation of a waveform of the physiological parameter;and outputting, by the speaker, the audio recording of the environment.7. The synchronizer of claim 4, wherein the operations further comprise:identifying a voice notation in the audio recording of the environment;determining, based on the aligned data, a discrete time in the timeinterval when the voice notation occurred; and generating a recordassociated with the patient, the record indicating the voice notationand the discrete time when the voice notation occurred.
 8. Thesynchronizer of claim 7, wherein identifying the voice notationcomprises determining that a rescuer has administered a treatment to thepatient by performing speech-to-text on the audio recording, and whereinthe record further indicates the treatment administered to the patient.9. The synchronizer of claim 4, wherein the marker comprises a power upsound of the medical device, a power off sound of the medical device, anaudible instruction output by the medical device, or an alarm output bythe medical device.
 10. The synchronizer of claim 4, wherein the medicaldevice comprises a defibrillator.
 11. The synchronizer of claim 4,wherein the physiological parameter comprises an electrocardiogram(ECG), an oxygenation of the patient's blood, an amount of carbondioxide in the patient's breath, a heart rate of the patient, a bloodpressure of the patient, a carboxyhemoglobin level of the patient'sblood, a temperature of the patient, a respiration rate of the patient,or a pulse rate of the patient.
 12. The synchronizer of claim 4, whereinthe recorder device comprises a mobile device or a wearable device. 13.A method, comprising: receiving, from a first device, a first filecomprising first measurements of a first parameter at first discretetimes in a time interval, the first file further comprising a markeroutput by the first device during the time interval; receiving, from asecond device, a second file comprising second measurements of a secondparameter at second discrete times in the time interval; detecting themarker output by the first device in the second measurements of thesecond parameter; based on detecting the signal output by the firstdevice in the second measurements, generating aligned data bytime-aligning the first measurements of the first parameter and thesecond measurements of the second parameter; and outputting the aligneddata.
 14. The method of claim 13, wherein the first device comprises adefibrillator and the second device comprises a mobile device or awearable device.
 15. The method of claim 13, wherein the first parametercomprises an electrocardiogram (ECG) of a patient, an oxygenation of thepatient's blood, an amount of carbon dioxide in the patient's breath, aheart rate of the patient, a blood pressure of the patient, acarboxyhemoglobin level of the patient's blood, a temperature of thepatient, a respiration rate of the patient, or a pulse rate of thepatient, and wherein the second parameter comprises sound, the secondmeasurements comprising an audio recording.
 16. The method of claim 15,wherein the marker comprises a power up sound of the first device, apower off sound of the first device, an audible instruction output bythe first device, or an alarm output by the first device.
 17. The methodof claim 15, wherein outputting the aligned data comprisessimultaneously: displaying, on a screen, an animation of a waveform ofthe first parameter; and outputting, by a speaker, the audio recording.18. The method of claim 15, further comprising: identifying words byperforming speech-to-text on the audio recording; and generating arecord comprising the words and the first measurements of the firstparameter.
 19. The method of claim 18, further comprising: determiningthat a treatment has been administered to a patient based on the words,wherein the record indicates the treatment administered to the patient.20. The method of claim 18, further comprising: transmitting the recordto an external computing device.